I just rebased all the commits, it's all in your hands now !

brilliant, hope this gets approved

I'll repost here what I said on discord:

I temporarly pushed it to docker hub for anyone wanting to try it out but who don't want to build it: https://hub.docker.com/r/ano002/overseerr-lidarr
I'll delete it as soon as it gets merged.

And also:

Now that I'm using only the lidarr overseerr I found some bugs:

• the Jobs & Cache page crashes in settings
• even though they are in the backend I forgot to add the possibility change music quotas etc for users in the frontend

If you have found any other issues please report them to me

the Jobs & Cache page crashes in settings

Just fixed this

Even though they are in the backend I forgot to add the possibility change music quotas etc for users in the frontend

Fixed this too

Thank you, @ano0002, for your hard work. I've found another bug: accessing Overseerr via HTTPS results in the following error:

[blocked] The page at https://overseerr.domain.com/ requested insecure content from http://IP:PORT/MediaCover/396/poster.jpg?lastWrite=ID. This content was blocked and must be served over HTTPS.

However, it works relatively fine when accessed via HTTP. Specifically, the artist posters are displayed correctly using HTTP when an artist page is opened but not on the music page.

Thanks for reporting that, I was aware of the issue and didn't have time to fix it yet. Will fix when I have time.

For any issues that arise could you please put them in: https://github.com/ano0002/overseerr/issues as it will make it easier to keep track

The Lidarr API should now work as expected (at least to add stuff, the scanning part hasn't changed)

Pushed the latest commit to docker

!!!
If you are using the lidarr fork and have been experiencing issue with the lidarr requests please pull the latest image from docker for both lidarr and overseerr-lidarr. I finally managed to find a fix which is reliable. The scans however might still have issues as I haven't gotten around to it yet.

Tremendous work here! Is there any specific areas of testing that you'd like to give extra attention?

I haven't fixed the lidarr scan and the UI requesting elements from lidarr directly so not those. But requesting should work for both artists and releases, artist are not always marked as available though. I also don't really know how I should make the search work, rn I'm not satisfied with how it works. I think there isn't anything specifically but if you find new bugs feel free to report them.

Good afternoon. I want to see how the integration with ldap works, I'm trying to run docker. It gives an error when starting. What should I do to launch the docker container?

yarn run v1.22.19
error Couldn't find a package.json file in "/app"
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Good afternoon. I want to see how the integration with ldap works, I'm trying to run docker. It gives an error when starting. What should I do to launch the docker container?

yarn run v1.22.19
error Couldn't find a package.json file in "/app"
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

What does your docker compose look like ?

version: '3'
services:
  overseerr:
    build:
      context: https://github.com/ano0002/overseerr.git#overseer-with-lidarr-support
      args:
        COMMIT_TAG: c105f10420049d1ade2eb28a6ae8335e96507e74
      dockerfile: Dockerfile.local
    ports:
      - 6165:5055
    volumes:
      - /srv/config/overseerrlidarr:/app:rw,cached
      - /app/node_modules
      - /app/.next

You haven't mapped anything to /app

version: '3'
services:
  overseerr:
    build:
      context: https://github.com/ano0002/overseerr.git#overseer-with-lidarr-support
      args:
        COMMIT_TAG: c105f10420049d1ade2eb28a6ae8335e96507e74
      dockerfile: Dockerfile.local
    ports:
      - 6165:5055
    volumes:
      - /srv/config/overseerrlidarr:/app:rw,cached
      - /srv/config/overseerrlidarr:/app/node_modules
      - /srv/config/overseerrlidarr:/app/.next

yarn run v1.22.19
error Couldn't find a package.json file in "/app"
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I've mapped all the folders. The error about missing files is still preserved.

version: '3'
services:
  overseerr:
    build:
      context: https://github.com/ano0002/overseerr.git#overseer-with-lidarr-support
      args:
        COMMIT_TAG: c105f10420049d1ade2eb28a6ae8335e96507e74
      dockerfile: Dockerfile.local
    ports:
      - 6165:5055
    volumes:
      - /srv/config/overseerrlidarr:/app:rw,cached
      - /srv/config/overseerrlidarr:/app/node_modules
      - /srv/config/overseerrlidarr:/app/.next

yarn run v1.22.19 error Couldn't find a package.json file in "/app" info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I've mapped all the folders. The error about missing files is still preserved.

I had the same problem and switching from bind mount to docker volumes fixed it. It appears that for whatever reason (permissions?) this is one that just won't work correctly with bind mounts unless you want to pre-download everything into your mount folder first. I had the same issue with the emqx docker too and just gave up on fighting that one after many days of fighting it.

Pushed a new build to docker with some fixes

First of all thanks for all the job you done @ano0002.
I have some question please:

1. Why still having the PR in draft since it's ready to deploy now no other work needs to be done to it other than bug fix.
2. Are you planning to add this change on jellyseerr?

First of all thanks for all the job you done @ano0002.
I have some question please:

1. Why still having the PR in draft since it's ready to deploy now no other work needs to be done to it other than bug fix.
2. Are you planning to add this change on jellyseerr?

1. I expect to have a fork with fewer bugs to deploy and merge it. However you can use the docker image I host if you can't wait and/or want to help me track bugs.

2. No, I'm not using it and adding it to Overseerr already took a long time so no

I am new to the whole docker ecosystem. Currently using Unraid. I did the docker pull and then docker run. How do I get the apps linked so music shows up in Overseerr? Any help would be greatly appreciated!

version: '3'
services:
  overseerr:
    build:
      context: https://github.com/ano0002/overseerr.git#overseer-with-lidarr-support
      args:
        COMMIT_TAG: c105f10420049d1ade2eb28a6ae8335e96507e74
      dockerfile: Dockerfile.local
    ports:
      - 6165:5055
    volumes:
      - /srv/config/overseerrlidarr:/app:rw,cached
      - /srv/config/overseerrlidarr:/app/node_modules
      - /srv/config/overseerrlidarr:/app/.next

yarn run v1.22.19 error Couldn't find a package.json file in "/app" info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I've mapped all the folders. The error about missing files is still preserved.

I had the same problem and switching from bind mount to docker volumes fixed it. It appears that for whatever reason (permissions?) this is one that just won't work correctly with bind mounts unless you want to pre-download everything into your mount folder first. I had the same issue with the emqx docker too and just gave up on fighting that one after many days of fighting it.

While I appreciate you pointed to the solution, alot of us here are clueless to how to mount to docker volumes. I ask chatGPT for help and this solved the issue:

version: '3'
services:
overseerr:
build:
context: https://github.com/ano0002/overseerr.git#overseer-with-lidarr-support
args:
COMMIT_TAG: c105f10
dockerfile: Dockerfile.local
ports:
- 6165:5055
volumes:
- overseerr_config:/app
- overseerr_node_modules:/app/node_modules
- overseerr_next:/app/.next

volumes:
overseerr_config:
overseerr_node_modules:
overseerr_next: